Communications control between mobile device and peripheral device

ABSTRACT

A non-transitory computer-readable medium can include instructions for performing a method that includes docking a mobile device with a docking station using at least one physical connection and at least one wireless connection to provide communication between the mobile device and the docking station. One of the physical or wireless connections can be selected for providing a signaling channel for communication of signaling data between the mobile device and the docking station. Independently of the signaling channel, one of the physical or wireless connections can be selected for providing a media channel for communication of media data between the mobile device and the docking station.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/829,302, filed Mar. 14, 2013, and entitled COMMUNICATIONS CONTROLBETWEEN MOBILE DEVICE AND PERIPHERAL DEVICE, the entire contents of eachof the above-identified application is incorporated herein by reference.

TECHNICAL FIELD

This disclosure relates to a controlling communications between a mobiledevice and a peripheral device.

BACKGROUND

Computing devices, including portable (e.g., mobile) devices, such ascellular telephones, tablet computers, notebook computers and the like,can couple to various types of peripheral devices to expand theircapabilities. One type of such peripheral is a docking station, whichoperates as an accessory to make a portable device operate with featuresand ergonomics commensurate with a more fixed version of the device. Forexample, as mobile telephones are being utilized more frequently forpersonal as well as business usage, a docking station can provideergonomics functionality of traditional desktop telephones. There arealso a variety of different functions that can be implemented by thedocking station and the mobile device. Such functions can vary dependingon whether the mobile device is docked or undocked with the dockingstation.

SUMMARY

This disclosure relates generally to controlling communications betweena mobile device and a peripheral device (e.g., a docking station).

As one example, a computer-readable medium can include instructionsexecutable by a processing resource. The instructions can includeconnection logic to provide connection data identifying which of atleast two connections is available for communication between a mobiledevice and a peripheral device when the mobile device is docked with theperipheral device. A signaling manager can control a signaling channelfor communication of signaling data over a first connection of the atleast two connections between the mobile device and the peripheraldevice. The first connection can be selected from the at least twoconnections based on the connection data. A media manager can control amedia channel for communication of media data over a second connectionof the at least two connections between the mobile device and theperipheral device based on the connection data. The first connection andthe second connection can be selected independently.

As another example, a non-transitory computer-readable medium can storeinstructions for performing a method. The method can include docking amobile device with a docking station using at least one physicalconnection and at least one wireless connection to provide communicationbetween the mobile device and the docking station. The method can alsoinclude selecting one of the physical or wireless connections forproviding a signaling channel for communication of signaling databetween the mobile device and the docking station. The method can alsoinclude independently of the signaling channel, selecting one of thephysical or wireless connections for providing a media channel forcommunication of media data between the mobile device and the dockingstation.

As yet another example, a system can include a mobile device andperipheral device (e.g., a docking station). The mobile device caninclude at least one wireless interface configured to communicate with aperipheral device using a wireless communications protocol and at leastone physical interface configured to communicate the peripheral deviceusing a physical communications protocol. The mobile device can alsoinclude connection control configured to select which of the wirelessand physical interfaces to utilize for communicating signaling data overa signaling channel between the mobile device and the peripheral deviceand media data over a media channel for over a selected connectionbetween the mobile device and the peripheral device. The peripheraldevice can also include a connection controller configured to control aplurality of connections to communicate the signaling data and the mediadata with the mobile device over each respective connection that isselected by the connection control.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example of a system of a mobile device docked with aperipheral device.

FIG. 2 depicts an example of a mobile device that can be implemented fordocking with a peripheral device.

FIG. 3 depicts an example of a peripheral device.

FIG. 4 depicts is a signaling diagram demonstrating an example ofestablishing a connection between the mobile device and a peripheraldevice.

FIG. 5 is a signaling diagram demonstrating an example of signaling thatcan occur in response to docking a mobile device to a peripheral deviceduring a VOIP call.

FIG. 6 is a signaling diagram demonstrating an example of signaling thatcan occur in response to docking a mobile device to a peripheral deviceduring a VOIP call.

FIG. 7 is a signaling diagram demonstrating an example of signaling thatoccur in response to answering an incoming VOIP call at the peripheraldevice.

FIG. 8 is a signaling diagram demonstrating an example of placing anoutgoing call through the mobile device via user inputs at a peripheraldevice.

FIG. 9 is a signaling diagram depicting an example of signaling that canoccur during a handover from a VOIP call to a cellular call.

FIG. 10 is a signaling diagram demonstrating an example of signalingthat can occur during a handover of a cellular call being to a VOIPcall.

DETAILED DESCRIPTION

This disclosure relates to controlling communications between a mobiledevice and a peripheral device, such as a docking station. The mobiledevice can be configured to establish multiple connections to theperipheral device. For example, the mobile device and the peripheral canbe coupled together via one or more physical communication connections,such as to provide for communication of electrical or optical signalsbetween ports of the respective devices. Additionally or alternativelythere may be one or more wireless connections for communications betweenthe mobile device and the peripheral device. Each of these connectionscan be utilized for communicating media data and signaling data.Controls can select which of the connections are to be utilized forcommunicating each of the media data and signaling data between themobile device and the peripheral device. Thus, a media channel forcommunicating media data and a signaling channel for communicatingsignaling data can be controlled independently, such that the media dataand signaling data may be communicated via the same or differentconnections. The determination as to which of the connections isutilized for each of the media channel and the signaling channel can bebased on one or more operating parameters, such as which connections areavailable, the type of access technology being utilized for implementinga media call, proximity of the media device relative to the peripheraldevice to which it is docked, or a combination of these or otheroperating parameters.

FIG. 1 depicts an example of a system 10 that includes a mobile device12 and a peripheral device 14. The mobile device 12 can be any portablemulti function device, such as a cellular telephone, smart phone,personal digital assistant (PDA), tablet computer, notebook computer orthe like. The mobile device 12 can be docked with respect to theperipheral device 14 via one or more connections 16 and 18. For example,each of the connections 16 and 18 can be implemented as a physicalconnection, such as an electrical connection (e.g., a multi pinconnection) or an optical connection (e.g., optical fiber) or acombination thereof. Additionally or alternatively, each connection 16or 18 can be implemented as a wireless connection. Examples of wirelessconnections that can be implemented for docking the mobile device 12with respect to the peripheral device 14 can include wirelesscommunication technologies implemented according to a radio frequency(RF technology), such as one of the Bluetooth standards, wireless USB,near field communications (e.g., up to about 0.2 meters), WIFI (e.g.,one of the 802.11X standards) as well as other wireless communicationtechnologies (e.g., the use of light, such as infrared, magnetic, soundor electric fields). Thus, as used herein in the context of a mobiledevice and peripheral device, the term “docked” and its semanticvariants refer to a communication that is established between thedevices over one or more of connections 16 and 18, which can includephysical connections, wireless connections or a combination of physicaland wireless connections. The types of communication technologies thatcan be utilized to provide the one or more connections 16 and 18 willdepend on the capabilities of the mobile device 12 and the peripheraldevice 14.

Additionally, while two such connections 16 and 18 are demonstrated inthe example of FIG. 1, there can be other numbers of possibleconnections greater than two for docking the devices 12 and 14. In theexample of FIG. 1, the mobile device includes a plurality ofcommunication interfaces 20 and 22 indicated at I/F 1 through I/F M,where M is a positive integer greater than or equal to two denoting thenumber of communication technologies that can be utilized for dockingwith a peripheral device 14. As used herein, the term ‘docked’ or‘docking’ or variations thereof refers to establishing an authenticatedconnection that can provide for communication between the mobile deviceand the peripheral device 14. The communication can includeunidirectional or bi-directional communication of data.

For the example of a physical communication technology providing one ormore of the connections 16 and 18, the physical connection can be madeby direct contact between connectors (e.g., male and female parts) ofthe mobile device 12 and the peripheral device 14. In other examples,the physical connection 16 or 18 can be established through a cable orother connecting element that may attach to an appropriate port of oneor both of the mobile device and peripheral device. Such physicalconnections can be in various configurations and form factors dependingon the model and manufacturer of the respective devices 12 and 14.

As a further example, each interface 20 and 22 of the mobile device 12can be communicatively coupled to a corresponding interface 24 and 26 ofthe peripheral device 14 via the respective connections 16 and 18. Whilein the example of FIG. 1, each of the mobile device 12 and theperipheral device 14 is illustrated as containing the same number of Mcommunication interfaces, it is to be understood and appreciated thateach can implement different numbers of such interfaces. In someexamples, the peripheral device 14 can be implemented as including agreater number of communication interfaces 24-26 than the mobile device12, such as to allow the peripheral device to accommodate a variety ofdifferent mobile devices (e.g., different models and/or differentvendors). In other examples, the mobile device 12 may be configured toinclude a greater number of communication interfaces 20-22 than theperipheral device 14.

The mobile device 12 can be configured to provide for communication ofmedia data over a media channel between the mobile device and theperipheral device 14. The mobile device 12 can also be configured tocommunicate signaling data over a signaling channel between the mobiledevice 12 and the peripheral device 14. As mentioned above, thecommunication can be unidirectional or bidirectional over eachrespective channel. The media data can include audio data, video data ora combination of audio and video data. The signaling data can includecommands, instructions, or status information associated with operationof the mobile device 12 or the peripheral device 14. In some examples,the media data can be communicated as part of a media call sessionbetween the mobile device 12 and one or more third parties incommunication with the mobile device 12 via a network 30.

The network 30 can include a local area network, a wide area network ora combination of local area and wide area networks, which can includeone or more of wireless or physical network structures. The network 30can be implemented according to one or more network topologies, such ascan include a wide area network (WAN, e.g., such as the Internet), alocal area network (e.g., LAN), a private area network (PAN) or acombination thereof. The network 30 can further include one or morephysical or wireless networks, such as a cellular telephone network, awireless local area network, a metropolitan area network or other formsof networks, each of which can employ a respective communicationsprotocol that can vary depending on the medium.

The mobile device includes a connection control 28 to control which ofthe connections 16 or 18 is utilized for each of the respectivesignaling channel and the media channel. The connection control 28 caninclude connection logic 32 that can provide information (e.g., statusinformation) about each of the connections 16 and 18. For example, theconnection logic 32 can provide connection data that identifies whichone or more of the connections are available to provide communicationsbetween the mobile device 12 and the peripheral device 14. Theconnection can be available, for example, when one or both of theconnections 16 and 18 have been authenticated to enable communicationsuch as when the mobile station is docked at the peripheral device 14.The connection logic 32 can also be programmed to control how theconnections 16 and 18 are established based on operating parameters ofone of both of the devices 12 and 14.

As an example, the connection logic 32 can be programmed to preventenabling one of the connections 16 from being established unless anotherof the connections 18 has already been established. For example, theconnection logic may be programmed to prevent a wireless connection(e.g., Bluetooth or other short range communication technology) frombeing authenticated to enable communication between a mobile device 12and peripheral device 14 unless a physical connection (e.g., connection18) has first been detected. In this way, the connection logic 32 mayhelp prevent an inadvertent docking between a mobile device and theperipheral device without a user first manually docking the mobiledevice with the peripheral device 14. However, the connection logic 32can be programmed to override such docking prevention in response to auser input instruction (e.g., made at the docking station) to forcedocking the mobile device with the docking station via a wirelessconnection. The particular algorithm that is utilized to control onwhich connection each of the media channel and signaling channel iscommunicated can vary depending upon the types of communicationtechnologies utilized by each of the interfaces 20 and 22, for example.Additionally or alternatively the connection 16 through 18 that isutilized for communicating each of the media and signaling channels candepend on the type of communication access technology via which themedia is communicated to and from the mobile device 12. The connectioncontrol 28 thus can dynamically switch the media channel and/or thesignaling channel between respective connections based on these or otherparameters.

As a further example, the connection control 28 can include a signalingmanager 34 and a media manager 36 each of which independently cancontrol which connection 16 through 18 are used to provide therespective signaling channel and media channel for communication betweenthe mobile device 12 and the peripheral device 14. The signaling manager34 can be programmed to control the signaling channel for communicationof signaling data over one of the connections 16 or 18 that has beenauthenticated for communication between the mobile device and theperipheral device. The decision can be based on the connection dataprovided by the connection logic 32. Similarly, the media manager 36 canbe programmed to control the media channel for communication of mediadata over a selected one of the connections 16 or 18 between the mobiledevice 12 and the peripheral device 14 based on the connection data. Theindependent control of the media channel and the signaling channel canafford the system 10 improved audio quality and flexibility according tothe types of connections that may be established. Such flexibilitybecomes relevant as one or more of the connections 16 through 18 may beenabled and disabled such as in response to attaching or removing themobile device relative to the peripheral device 14.

As mentioned above, the media channel can include media data that isreceived at the mobile device 12 via the network 30 associated with amedia session. To implement the media session, the mobile device 12 caninclude one or more media interface 38 and 40 demonstrated as Media IF/1through Media IF/N, where N is a positive integer denoting the number ofaccess technologies that can be utilized for communication of media viathe network 30. In some examples, each of the media interfaces 38 and 40can be implemented as wireless access technologies configured tocommunicate electromagnetic signals that can use any of a number ofcommunication standards, protocols and technologies such as includingglobal system for mobile (GSM), code division multiple access (CDMA),time division multiple access (TDMA), wideband-CDMA (W-CDMA), WIFI(e.g., one of the IEEE 802.11X standards), wireless metropolitan areanetworks (WirelessMAN), such as WiMax, satellite radio, two-way (orhalf-duplex) radio and the like. Additionally or alternatively, themobile device 12 can employ other wireless data protocols (e.g., GeneralPacket Radio Service (GPRS), Enhanced Data rates for GSM Evolution(EDGE), Universal Mobile Telecommunications System (UMTS)) that permitconcurrent voice and data over the same network, which such data can beutilized for conducting a VOIP call session. Those skilled in the artwill understand and appreciate that various standards and protocolsexist and have yet to be developed to enable communication via these andother radio technologies.

The mobile device 12 can also include a call control module 42 that canselectively control which of the media interfaces 38 and 40 is utilizedfor conducting the media session. The call control 42 can also handlecall set up and termination via one or more of the access technologies.In some examples, the call control 42 can switch or handover an ongoingmedia session from one access technology to another access technology.Examples of mechanisms that can be implemented by the call control 42for controlling handover between different access technologies aredisclosed in U.S. Pat. No. 8,140,079, entitled SYSTEM AND METHOD TOFACILITATE HANDOVER, which is incorporated herein by reference. Otherapproaches for implementing handover between access technologies can beutilized by the call control 42 including known approaches as well asthose that may be subsequently developed.

In some examples, the call control 42 can provide information to theconnection control 28 with media interface data identifying which of theaccess technologies and interfaces 38 and 40 is utilized forcommunicating the media data relative to the network 30. The callcontrol 42 can also provide media interface data to indicate if ahandover is being implemented between the different access technologiesimplemented by the respective interfaces 38 and 40. For example, theconnection control 28, including the media manager 36 and/or thesignaling manager 34, can utilize the media interface data, which candescribe media session parameters, to dynamically control and modifywhich of the connections 16 and 18 is utilized for the respectivesignaling channel and the media channel.

It is to be understood that the various blocks and functions disclosedin the mobile device 12 and the peripheral device 14 in the examplesystem 10 can be implemented as software (e.g., stored on anon-transitory medium or media), hardware (e.g., a processor orcontroller executing instructions), or as a combination of software andhardware.

FIG. 2 depicts an example of a mobile device 50. The mobile device 50can be configured to connect with a peripheral device, such as a dockingstation (e.g., the peripheral device 14 of FIG. 1). The mobile device 50can include memory 52, which may include one or more non-transitorycomputer readable storage media, a memory controller 54 and a processingresource 56. The processing resource 56 can be implemented as includingone or more processor cores. The memory controller 54 and processingresource 56 can be coupled to a component interface 58 via an internalbus 60. There can be any number of one or more buses implemented withinthe mobile device to enable communication between the respectivecomponents implemented in the mobile device 50.

The mobile device 50 also includes audio circuitry 62 coupled to theinterface 58. One or more speakers 64 and one or more microphones 66 canbe coupled to the audio circuitry to provide an audio interface betweenthe mobile device 50 and the user. The speaker 64 can convert electricalsignals from the audio circuitry 62 into audible sound. The microphone66 can convert audible (e.g., voice) signals to an electrical signalthat is provided to the audio circuitry 62. The respective audio signalscommunicated to and from the audio circuitry 62 can further becommunicated to the component interface 58 and distributed to othercomponents via the internal communication bus structure.

The mobile device 50 can also include a multi-channel I/O port 68, ashort range wireless transceiver 70, a cellular transceiver 72, a WLANtransceiver 74 as well as other forms of communication devices and/orsensors demonstrated schematically as “other” 76. Each of the respectiveports and transceivers 68, 70, 72, 74, and 76 can be communicativelycoupled with the component interface 58. An I/O subsystem 78 can also becoupled to the component interface 58 for connecting to otherinput/output components, such as including a touch screen 80 as well asone or more other input devices 82 (e.g., keys, buttons or other userinput mechanisms). The I/O subsystem 78, for example, can includecontrollers for controlling communication of I/O components 80 and 82.

The memory 52 can include volatile memory (e.g., random access memory)as well as non-volatile memory (e.g., magnetic disc storage, flashmemory, solid state memory or the like). The memory controller 54 cancontrol access to the memory by the processing resource 56 and the othercomponents in the system that are coupled to the component interface 58.The memory 52 can also include an operating system 84, a telephoneapplication 86 as well as one or more other applications 88, which maybe resident in the memory for performing the basic functions of themobile device 50. For example, the operating system 84 can be programmedto communicate with an authenticated remote device (e.g., a dockingstation) automatically using a prescribed protocol (e.g., Bluetooth) viathe transceiver 70. Some applications further may be installed by a usersuch as downloaded from a remote location (e.g., a server or anothercomputer).

The memory 52 can also include a mobility application 90 that isprogrammed to provide or extend a unified communications. For example,the mobility application 90 can employ the existing telephoneapplication 86 in conjunction with one or more of the device components,such as the cellular transceiver 72, the WLAN transceiver 74 or thecommunication mechanisms 76, for making, receiving and conducting callsacross one or more networks. For example the mobility application 90 canemploy least cost routing rules and quality of service to control whichaccess technology to utilize for a given call. In this context, the callcan include any form of media including audio, video or a combination ofaudio and video.

The mobility application 90 can include call control 92 as well asconnection control 94. The connection control 94 can include connectionlogic 96 to control and authenticate connections between the mobiledevice 50 and a peripheral device (e.g., a docking station) as disclosedherein. The connection logic 96 can also provide connection data 98,which can be stored in the memory 52 for identifying which connection orset of connections is available for communication between a mobiledevice and a docking station. The connection data thus can identify whena mobile device is docked with a docking station as well as identify theparticular connections and mobile device components operative to providecommunication over each respective connection. Since the types ofconnection between the mobile device 50 and a docking station can changedynamically over time, such as in response to physically attaching andremoving the mobile device from one or more connections, the connectionlogic 96 can maintain the state of such connections as part of theconnection data 98. In some examples, the connection data and theconnection state information can be maintained as part of a statemachine.

A signaling manager 100 can employ the connection data 98 to controlwhich of the available connections will provide the signaling channelfor communication of signaling data between the mobile device 50 and adocking station to which the device has been docked. The connectioncontrol 94 also includes a media manager that is programmed to utilizethe connection data for controlling a media channel for communication ofmedia data over a selected one of the available connections between themobile device 50 and a docking station to which it has been docked. Eachof the signaling manager 100 and the media manager 102 independentlycontrols its respective channel and thus can employ differentmethodologies and algorithms to determine which connection to utilizefor communication of the respective channels. Because the connectioncontrols 94 decouples the signaling channel from the media channel amore robust and adaptive docking session can be realized.

By way of further example, the call control 92 can include handoverlogic 104 to control changes between different access technologies. Forexample, the handover logic 104 can implement an approach to utilizeleast cost routing for a media call be selectively making or receiving acall over one wireless access technology and transfer the call toanother wireless access technology depending on the rules implemented bythe handover logic. In some examples, the handover logic 104 can controlimplementing the calls through the cellular transceiver 72 and the WLANtransceiver 74 such as for conducting a VOIP call. A VOIP call can beimplemented over any VOIP access technology, which can include VOIP overcellular data, VOIP over a WLAN or VOIP over any other access technologyconfigured to support VOIP using physical or wireless networks. Theavailable communication with the docking station can be via themulti-channel I/O port 68, the short range wireless transceiver 70 aswell as one or more other connections that might exist between themobile device and the docking station.

In some examples, the connection logic 96 can be programmed to disableestablishing a connection using one of the I/O port 68 or transceiver 70until another one of the connections has been authenticated andestablished between the mobile device and the docking station. Forinstance, the connection logic 96 can selectively enable a wirelessconnection via the short range wireless transceiver 70 based on controlinformation that is stored in the connection data 98 indicating that anauthenticated physical connection (e.g., via I/O port 68) alreadyexists. The control information can be derived from determining theauthenticated connection has been established via the multi-channel I/Oport 68 and a corresponding port of a docking station, which can bestored as part of the connection data 98. In some examples, thesignaling manager 100 can give priority to the physical connection viathe multi-channel I/O port 68 over the corresponding wireless connectionvia the wireless transceiver 70 with the docking station. However in theabsence of the physical connection being established, the mobile device50 can utilize the wireless transceiver 70 for the signaling channel.Additionally, if the mobile device is no longer docked with the dockingstation the media channel with route through the audio resources of themobile device namely the speaker 64 and the microphone 66. This can beimplemented in the hands free speakerphone mode or in a conventionalhandset mode for the mobile device.

In some examples, the media manager 102 can selectively control which ofthe multi-channel I/O port 68 or via the short range wirelesstransceiver 70 is utilized for communication of the media channel basedon the access technologies that is specified by the call control 92. Asmentioned above, other data 106 can include media interface dataspecifying which access technology and/or respective transceiver 72, 74,76 is utilized for communicating media data over a network.

As an example, the media manager 102 can be programmed to communicatethe media channel over a physical channel (the multi-channel I/O port68) based on the connection data 98 indicating that the mobile device 50is docked with the docking station and in response to the mediainterface data specified in the other data 106 indicating a handoverfrom a cellular access technology (e.g., via the cellular transceiver72) to a VOIP access technology (e.g., via the WLAN transceiver 74).That is, the media manager 102 can utilize the physical connection(e.g., via the multi-channel I/O port 68) with the docking station forVOIP calls which can be wireless VOIP or VOIP over a physical network.

As another example, if the handover logic 104 has triggered a handoverfrom the VOIP access technology to cellular, which handover conditioncan be stored as part of the other data 106, the media manager 102 cancontrol the components 70 and 76 to provide for communicating the mediachannel via the wireless transceiver 70 and not the physical connectionvia the multi-channel I/O port 68. If the connection logic 96 determinesthat wireless connection between the wireless transceiver 70 and thedocking station is lost, the media manager 102 can switch the mediachannel from the wireless connection back to the multi-channel I/O portprovided it also still exists. If the connection logic 96 determinesthat the mobile device 50 is no longer docked with the docking station,the media manager 102 can route the media data with respect to audiocircuitry of the mobile device.

In some examples, the handover logic 104 can control the handoverbetween VOIP and cellular access technologies based on the connectiondata 98 indicating whether or not the mobile device 50 is docked withthe docking station. For instance, the handover logic 104 of the callcontrol 92 can prioritize VOIP media connection when the connection data98 indicates that the mobile device is docked. As an example, thehandover logic 104 of the call control 92 can implement call qualitymetrics (e.g., based on one or more of received signal strength,transmit power, bit error rate, packet error rate) and implementhandover based on the metric indicating call quality below a prescribedthreshold. In response to connection data indicating that the mobiledevice 50 is docked, the call control can adjust the threshold to makehandover more difficult, thereby prioritizing VOIP media sessions whendocked. In some examples, the handover logic can disable handing over aVOIP call to a cellular call, unless the VOIP connection is dropped.Other call metrics can be utilized to prioritize VOIP media while themobile device is docked.

As a further example, whichever of the connections is utilized forsignaling, as controlled by the signaling manager 100, the connectioncontrol 96 can include a data extractor that can receive an encapsulatedmessage that is provided via the signaling channel. For example, inresponse to user inputs received at a user input device (e.g., a keypad)at a docking station, the docketing station can communicate such inputsencoded in the signaling channel. The connections control 94 can receivethe encoded input data and the data extractor 108 can extract theencoded data to provide corresponding instructions for controlling themobile device 50 based on the inputs at the docking station. Forinstance, the user input can be used to control the telephoneapplication such as for dialing or implementing other key commands onthe mobile device 50.

By way of further example, the call control 92 can be responsive to thedata encoded in the user input message that is encapsulated in thesignaling channel for implementing a VOIP access technology mediasession, such as via the WLAN transceiver 74. For instance, the callcontrol 92 can utilize the user input information, such as correspondingto a button down and button up duration, and convert encoded button upand button down data to provide instructions for implementing the VOIPcall via the WLAN transceiver. The data encoded in the user inputmessage can include data specifying a source of the information (e.g.,which of a plurality of different buttons) as well as a time when theuser input device (e.g., button) was activated and a time when it wasdeactivated. The call control can employ such data to determine whichbutton and a duration of when the button was down that can be utilizedfor making the VOIP call. For instance, the call control can providesignaling data back to docking station via the signaling channel toprovide a dual tone multi-frequency (DTMF) tones according to the buttonpressed and the duration that the button is pressed. In the examplewhere a wireless connection is utilized for the signaling channel, theuser inputs can be encoded according to a wireless protocol, such as theBluetooth Network Encapsulation Protocol (BNEP), for transferringapplication level data via the signaling path between the mobilityapplication 90 and the docking station. For example, BNEP or otherencapsulation protocol can be used to send user input messages from thedocking station to the mobile device, such as for dialing or otherrelated call controls. Additionally, BNEP or other encapsulationprotocol can be used to send update messages (e.g., firmware updates andthe like) from the mobile device 50 to the docking station.

FIG. 3 depicts an example of a peripheral corresponding to a dockingstation 150 that can be connected with a mobile device (e.g., mobiledevice 50 of FIG. 2 or mobile device 12 of FIG. 1). The docking station150 can include connectors and electronics to provide functionalitycommensurate with a desk phone such as including a keypad for dialing, aspeaker for conducting handsfree calls, and a handset that can beutilized for speaking and listening in private. While the example ofFIG. 3 demonstrates a phone for audio communication, it is to beunderstood and appreciated that additional functionality for videoconferencing and calls can be utilized and further may leverage audioand video capabilities of a mobile device that may be attached to thedocking station 150. In other examples, communications technology can bedistributed between the docking station 150 and a mobile device that candocked with the docking station via one or more connections.

The docking station 150 includes a control system 152 that is configuredto provide for audio processing and for docking a mobile device throughone or more connections, which can include a multi-pin connector 154 anda short range wireless connector 156. As an example, the short rangewireless connector 156 can be implemented by a Bluetooth module. Inaddition to the multi-pin connector 154 one or more other physicalconnectors 158 can be provided for connecting to the mobile device orother devices. Such connectors 158 can be implemented, for example, asUSB, fire wire or the like.

As an example, the multi-pin connector 154 can provide an external portthat is the same and/or similar to and/or compatible with a thirty-pinconnector used for various devices commercially available from AppleComputer, Inc. Other types of multi-pin connectors can also be utilizedwith form factors depending on the configuration and capabilities of themobile device that is to be docked with the docking station 150. Thedocking station 150 can also include additional ports, including anaudio output port 160 and a handset I/O port 162. The audio output port160 can be utilized to plug in an external speaker or headset, forexample. The handset I/O port 162 can be utilized for providing an audioconnection with a handset, such as through an RJ22 jack.

The station 150 can also include a keypad 164 as well as other userinput devices 166 that provide a human machine interface 167 forinterfacing with the functions provided by the station 150. The keypad164 can be numerical, alphanumerical or various other types of keypads.The user input devices 166 can include various buttons to accesspredetermined functionality of the station 150, such as including apower button (e.g., UI1) to turn on and off the station, as well as forimplanting other control functions. Such other control functions caninclude a button (e.g., UI3) for selectively activating the short rangewireless module 156. Another of the user input devices 166 (e.g., UIQ)can be implemented as a volume control for adjusting the volume that canbe provided via the audio output port 160, a speaker 168 or the handsetI/O port 162. Other user input devices 166 (e.g., UI1) can be utilizedto selectively activate and deactivate the speakerphone functionality,which employs one or more speakers 168 for providing audio output andone or more microphones 170 for receiving audio input from a user.Another user input device 166 (e.g., UI2) can be utilize to selectiveactivate and deactivate the handset I/O port 162 for enabling audioinput and output to be provided via the handset I/O port 162.

The control system 152 is configured to control various functionality ofthe station including connections that can be made with a mobile devicesuch as via the short range wireless module 156, the multi-pin connector154 or one or more other connectors 158. In the example of FIG. 3, thecontrol system 152 includes a device coprocessor 172, a codec/DSP 174, amicro controller 176, a bus interface 178, and memory 180. The memory180 can include logic that can store rules for controlling thefunctionality of the station 150 and the use of its various componentsin response to user inputs, such as can be made via the human machineinterface 167 and/or the keypad 164. Additionally or alternatively, thelogic 182 can control various components of the station 150 in responseto instructions or commands received via a signaling channel over aconnection using one or more of the connectors 154, 156 and/or 158.

In addition to communicating media data and signaling data viaconnections specified by a mobile device, the control system 152 can beconfigured to provide charging power to a mobile device that isconnected via the multi-pin connector 154 or the connector 158. Forexample, the other circuitry 184 can include a power source configuredto supply a predetermined charging voltage to the mobile device via oneor more of the pins of the multi-pin connector 154 or the otherconnectors 158. In this way, the mobile device that is physicallyconnected via one of the connectors 154 or 158 can continually chargewhile utilizing its processing resource and communication technologiesfor transmission of media data between the docking station 150 and anetwork such as disclosed herein.

FIGS. 4 through 10 illustrate examples of some signaling that can beimplemented between the mobile device and a peripheral device (e.g.,docking station) for performing the various functions disclosed herein.For sake of consistency, the same reference numbers refer to the sameparts in the various examples of FIGS. 4-10. In these examples, physicalactions or operations performed by a user 202 are demonstrated by arrowsoriginating from a user block and being performed with respect to amobile device 204 or a peripheral device 206, such as the dockingstation or other accessory. Lines having arrows on both sides areutilized to indicate signaling between multiple devices orbi-directional interaction, whereas a line with a single arrow indicatesthat communication from one device or user to another.

FIG. 4 provides an example of signaling for authentication between amobile device 204 and a peripheral device 206 over both a physical andwireless interface, such as Bluetooth. As a user 202 brings the mobiledevice 204 with a range of a short range wireless connection with aperipheral device 206 to which it has already been authorized (e.g., inresponse to a user configuration process), the peripheral device andmobile device can be paired and authenticated automatically to enablecommunication of media and signaling data. A user action can beperformed to physically dock the mobile device with the peripheraldevice, such as by creating a physical electrical connection between themobile device and peripheral device. Such physical connection enablesfurther authentication over the physical connection, such as a universalserial bus. At this stage audio, can be routed via USB or Bluetoothbetween the mobile device and the peripheral device. Next, a user mayundock a mobile device from the peripheral device, such that thephysical connection has disconnected and the wireless connection mayremain authenticated. From this connection mode, media can be routed tothe mobile device or the media and signaling channel can be provided viathe short range wireless connection. After a user takes the mobiledevice out of range for it to maintain the short range wirelessconnection, the connection may be broken or disconnected.

In the example of FIG. 5, the user 202 is shown as interacting with theperipheral device 206 and with the mobile device 204. In the example ofFIG. 5, it is presumed that the initial state of the mobile device is anactive VOIP call and that the handset of the peripheral device is in theoff hook position. In response to a user docking the mobile device 204to the peripheral device 206, the connection control of the mobiledevice issues a signaling request to the peripheral device via asignaling channel to obtain data specifying its operating status. Theperipheral device 206 can return a status reply to the connectioncontrol 208, such as to indicate audio LEDs state. The connectioncontrol can issue another request to the handset position data of thedocking station. In response, the peripheral device 206 can employ thesignaling channel (over the selected connection) to return an indicationof the handset position being off hook. In response to acquiring thestatus information for the peripheral device 206, the connection control208 of the mobile device can communicate media data to the peripheraldevice via a connection (e.g., wireless or physical connection) that isselected as disclosed herein. The control logic of peripheral device canin turn flow the audio to the user via the handset of the peripheraldevice 206 due to its off hook position. The call can continue with thecall audio being routed to the handset until the call session isterminated, such as in response to a user input via the user 202pressing an “end call button” on the mobile device.

In the example of FIG. 6, it is assumed that an active VOIP call isbeing conducted via the mobile device 204 before being docked to theperipheral device 206. The signaling demonstrates the user connects themobile device 204 to the peripheral device 206 thereby docking it andenabling interaction between the peripheral device and the mobile devicevia one or more connections. In response to being docked, the connectioncontrol 208 can issue a request for status of the peripheral device 206,such as a status that can be indicated by a state machine used to driveLEDs of the peripheral device. The peripheral device 206 can return anindication of the status of the respective components, such as via areturn get LEDS response. The connection control 208 can further requesta handset status via a handset position request, and the peripheraldevice can return the handset position, which in this example is onhook. The connection control 208 can further provide a command to theperipheral device to control audio on the peripheral device 206, whichcan include activating the speaker of the peripheral device to an ONcondition and illuminating the corresponding LED indicator. In responseto the command via the signaling channel, the peripheral device 206 canturn the speaker LED ON which can be visualized to the user via the LED.The media channel can be established over one of the availableconnections between the peripheral device and the mobile device asselected by the connection control 208 as disclosed herein.

For example, during an active VOIP call session, priority can be givento the physical connection (e.g., a multi-pin connection) to providemedia data over the media channel between the peripheral device 206 andthe mobile device 204. Resulting audio can flow to the speaker that hasbeen activated via the signaling command to set the speaker to the ONposition. Communication thus can be conducted in a hands free mode viathe speaker and microphone via the peripheral device. The call cancontinue until the user presses an end call button which in turn resultsin the connection control 208 issuing a command to turn the speaker OFF.The peripheral device 206 in turn responds to the command based on itslogic to turn the speaker off.

FIG. 7 demonstrates a signaling diagram for an example scenario where anincoming call is answered through a handset of the peripheral device206. In the example of FIG. 7, an incoming VOIP call is received at themobile device 204 (e.g., via call control utilizing a VOIP accesstechnology). The connection control 208 employs a signaling channel overa selected connection between the peripheral device and the mobiledevice 204 to provide a ringtone command. The peripheral device 206 inturn provides a ring tone to flow through its speaker or other indicatormechanism (e.g., a light) to indicate an incoming call. In this example,the user 202 manually picks the handset up, which can activate acorresponding switch at the peripheral device 206. Controls in theperipheral device 206 in turn send a handset position signal via thesignaling channel to the connection control 208 of the mobile device 204to indicate that the handset has been placed in the off hook condition.The connection control 208 can establish the media channel between theperipheral device and the mobile device over a selected connection basedupon the circumstances of the call. For example, being a VOIP call, thecall connection control can specify a physical connection if availablefor the media channel between the peripheral device and the mobiledevice 204. The audio or other media that is provided to the peripheraldevice 206 can in turn be provided to the handset by the peripheraldevice based on control logic implemented by the peripheral. At somepoint in this example, in response to the handset returning to an onhook position at the peripheral device 206, the peripheral device cansupply a notification of the handset position being placed on hook tothe connection control 208 via the signaling channel. The on hooksignaling information can be utilized by the connection control 208 toterminate the VOIP call.

FIG. 8 depicts an example of an outgoing VOIP call that can beimplemented via the peripheral device 206 in a hands free mode using thekeypad of the peripheral device. In the example of FIG. 8, in responseto a user pressing down on a digit on the keypad, the peripheral device206 can send a digit down signal for the identified digit via anestablished signaling channel to the connection control of the mobiledevice. The mobile device 204 can return a corresponding DTMF tone tothe peripheral device 206 via the signaling channel that has beenestablished over one of the connections between the peripheral deviceand the mobile device. The resulting DTMF tone can be flowed to thespeaker of the peripheral device and rendered as audible sound to theuser. Similarly, a “digit up” signal can be provided via the signalingchannel from the peripheral device 206 to the connection control 208 ofthe mobile device 204in response to a user releasing the digit of thekeypad, which can result in the mobile device terminating the DTMF toneprovided to the peripheral device 206. Additionally, the user can pickup the handset after completing the dialing of a desired telephonenumber. In response, the peripheral device 206 can provide anotification message of the handset position via the signaling channelbetween the peripheral device and the mobile device 204. The connectioncontrol 208 can provide a corresponding ring back tone to the peripheraldevice via the signaling channel, which can employ render an audiblering back tone to the handset that is off-hook. Once a call has beenconnected, media data corresponding to the call audio can becommunicated over the media channel that has been selected forcommunication of call audio between the mobile device 204 and theperipheral device 206. In this example, the corresponding audio would inturn flow to the handset that is currently off hook. Once the handsethas been placed back on hook (or the call is otherwise terminated at theperipheral device), the peripheral device 206 can provide acorresponding notification to the connection control 208 of the mobiledevice indicating that the position is on hook and the connectioncontrol can utilize this information to terminate the call via thecurrently utilized access technology at the mobile device.

FIG. 9 depicts an example of a handover situation in which a VOIP callis handed over to a cellular access technology. In the example of FIG.9, it is presumed that at least a physical connection and a wirelessconnection exist between the mobile device 204 and the peripheral device206. In the example of FIG. 9, to facilitate signaling flow, the systemdemonstrates a mobility application 210 of the mobile device asincluding both a signaling manager 212 and a media manager 214, whichcan form part of the connection control of the mobility application,such as disclosed herein. An incoming VOIP call is received by themobility application (e.g., call control thereof) 210, such as via asession initiation protocol (SIP) invite message. In response to theincoming VOIP call, a ringtone is supplied to the peripheral device on amedia channel over the established physical connection (e.g., USB orother). The peripheral device 206 can flow the corresponding ringtone tothe speaker according to execution of control logic of the peripheral.In response, a user can press the speaker button (or pick up a handset),which activates the speaker and associated LED to the ON condition atthe peripheral device. The peripheral device 206 in turn sends anotification via the signaling channel of the mobile device that thespeaker is in the ON condition. In response to the notification, themedia manager 214 can provide the call audio (e.g., media data) for theVOIP call on the media channel over the physical connection between theperipheral device and the mobile device. The peripheral device 206 canflow the audio to the speaker of the peripheral device, therebyproviding communication between the user and the peripheral device in ahands free manner over the speaker phone.

At some point in the example of FIG. 9, a handout from VOIP accesstechnology to a cellular access technology occurs (e.g., by handoverlogic of the mobility application 210). In response to the handover tocellular, the media manager 214 in turn can change the connection forthe media channel from the physical connection to a short range wirelessconnection, such as Bluetooth. The peripheral device 206, in response tothe change in the media channel, can provide the audio to the speakerwith minimum interruption to the user. At some point when the call hasfinished, the user can press the speaker button to turn the speaker andits associated LED to the OFF condition, and the peripheral deviceprovides a notification that the speaker has been turned to the offcondition via the signaling channel over the selected connection (e.g.,the physical connection). Since the call audio was over the short rangewireless protocol, the wireless protocol can further provide a hang uprequest from the peripheral device to the mobile device to end thecellular telephone call session.

FIG. 10 illustrates an example in which a media session over a cellularaccess technology is handed over to a VOIP access technology. In theexample of FIG. 9, it is presumed that at least a physical connectionand a wireless connection exist between the mobile device 204 and theperipheral device 206. An incoming cellular call is received at themobile device 204 and, in response, the operating system of the mobiledevice automatically can employ a protocol (e.g., Bluetooth) to providea ringtone to the peripheral device over the authenticated wirelessconnection. The peripheral device 206 can flow the correspondingringtone to the speaker to alert the user of the incoming call. A usercan press the speaker button of the peripheral device to answer thecall. The peripheral device 206 can in turn send an answer command viathe wireless protocol, as is known in the art. The peripheral device 206can also send a notification that the speaker has been activated to theON condition via the current signaling channel between the peripheraldevice and the mobile device. The information regarding the connectedcall can be communicated from the operating system to the mobilityapplication. In response to the cellular call being established themedia manager 214 can enable the media channel to be communicated viathe wireless connection (e.g., using Bluetooth). The peripheral devicecan flow the media to the speaker via the routing function implementedby the peripheral control.

At some point in this example, the cellular call is transferred to aVOIP access technology (e.g., by handover logic of the mobilityapplication 210). In response to detecting the call being transferred toVOIP, the media manager 214 can transfer the media data to a physicalconnection (e.g., USB). The peripheral device 206 can in turn flow themedia data (audio) received via the physical connection to the speaker.When it is desired to end the call, the user can press the speakerbutton to turn the LED off. The peripheral device 206 can in turn employthe signaling channel over the selected connection (e.g., the physicalconnection) to provide a notification that the speaker has been turnedto the off condition and the mobility application 210 can terminate thecall.

What have been described above are examples. It is, of course, notpossible to describe every conceivable combination of components ormethodologies, but one of ordinary skill in the art will recognize thatmany further combinations and permutations are possible. Accordingly,the disclosure is intended to embrace all such alterations,modifications, and variations that fall within the scope of thisapplication, including the appended claims. As used herein, the term“includes” means includes but not limited to, the term “including” meansincluding but not limited to. The term “based on” means based at leastin part on. Additionally, where the disclosure or claims recite “a,”“an,” “a first,” or “another” element, or the equivalent thereof, itshould be interpreted to include one or more than one such element,neither requiring nor excluding two or more such elements.

What is claimed is:
 1. A non-transitory computer-readable medium thatincludes instructions executable by a processor, the instructionscomprising: connection logic to provide connection data identifyingwhich of at least two connections is available for communication betweena mobile device and a peripheral device when the mobile device is dockedwith the peripheral device; a signaling manager to control a signalingchannel for communication of signaling data over a first connection ofthe at least two connections between the mobile device and theperipheral device, the first connection being selected from the at leasttwo connections based on the connection data; and a media manager tocontrol a media channel for communication of media data over a secondconnection of the at least two connections between the mobile device andthe peripheral device based on the connection data, the first connectionand the second connection being selected independently.
 2. The medium ofclaim 1, wherein the at least two connections between the mobile deviceand the peripheral device include a wireless connection and at least onephysical connection.
 3. The medium of claim 2, wherein the wirelessconnection comprises a short range radio frequency communicationstechnology and the physical connection comprises a multi-pin physicalconnection.
 4. The medium of claim 2, wherein the connection logic isfurther programmed to prevent using the wireless connection for themedia channel between the mobile device and the peripheral device unlessat least one of the physical connections is established or the wirelessconnection is enabled in response to a user input.
 5. The medium ofclaim 1, further comprising a call control programmed to provideinstructions to control at least one of a first media interface and asecond media interface for communicating the media data via differentrespective access technologies between the mobile device and a network.6. The medium of claim 5, wherein the call control is further programmedto control handover between first and second of the different respectiveaccess technologies and to provide media interface data indicating whichof the first and second of the different respective access technologiesis being used for communicating the media data between the mobile deviceand the network, the connection logic being further programmed tocontrol which of the at least two connections between the peripheraldevice and the mobile device is used for the media channel based on themedia interface data.
 7. The medium of claim 6, wherein the at least twoconnections between the mobile device and the peripheral device includea wireless connection and at least one physical connection, wherein themedia manager is programmed to communicate the media channel over thephysical connection based on the connection data indicating that themobile device is docked with the peripheral device and in response tothe media interface data indicating a handover from a cellular accesstechnology to a voice over internet protocol (VoIP) access technology.8. The medium of claim 6, wherein the at least two connections betweenthe mobile device and the peripheral device include a wirelessconnection and at least one physical connection, wherein the mediamanager is programmed to communicate the media channel via the wirelessconnection based on the connection data indicating that the mobiledevice is docked with the peripheral device and in response to the mediainterface data indicating a handover from a voice over internet protocolaccess technology to a cellular access technology.
 9. The medium ofclaim 8, wherein the media manager is further programmed to switch themedia channel from the wireless connection to a handset of the mobiledevice in response to losing the wireless connection.
 10. The medium ofclaim 5, wherein the call control is further programmed to mitigatehandover from a voice over internet protocol (VoIP) access technology toa cellular voice access technology in response to the connection dataindicating that the mobile device is docked with the peripheral device,whereby the VOIP access technology is prioritized relative to thecellular voice access technology while the mobile device is docked withthe peripheral device.
 11. The medium of claim 1, further comprising adata extractor to receive a user input message from the peripheraldevice via the signaling channel, the user input message encoding dataentered at the peripheral device via a user input device.
 12. The mediumof claim 11, further comprising a call control programmed to control afirst media interface for communicating the media data via a voice overinternet protocol access technology and a second media interface forcommunicating the media data via another access technology, each of thefirst and second media interfaces being resident in the mobile device,wherein the call control is responsive to the data encoded in the userinput message to control the first media interface for communicating themedia data via the voice over internet protocol access technologybetween the mobile device and a network.
 13. The medium of claim 1,wherein the connection logic is further programmed to disable one of theat least two connections until another of the at least two connectionshas been established between the mobile device and the peripheraldevice.
 14. The medium of claim 1, wherein the connection logic isfurther programmed to disable one of the at least two connections untilan activation message is received from the peripheral device via amessage in the signaling channel provided via another of the at leasttwo connections in response to a user input.
 15. The medium of claim 1,further comprising an update component to send an update message via thesignaling channel to update program instructions for operating theperipheral device.
 16. The medium of claim 1, wherein each of the firstconnection and the second connection is authenticated to enablecommunication of both the signaling channel and the media channelbetween the mobile device and the peripheral device.
 17. The medium ofclaim 16, wherein the peripheral device is a docking station and themobile device is a multi-function mobile telecommunications device. 18.A non-transitory computer-readable medium to store instructions forperforming a method that comprises: docking a mobile device with adocking station using at least one physical connection and at least onewireless connection to provide communication between the mobile deviceand the docking station; selecting one of the physical or wirelessconnections for providing a signaling channel for communication ofsignaling data between the mobile device and the docking station; andindependently of the signaling channel, selecting one of the physical orwireless connections for providing a media channel for communication ofmedia data between the mobile device and the docking station.
 19. Themedium of claim 18, wherein the method further comprises preventing useof each wireless connection for the media channel between the mobiledevice and the docking station unless at least one of a physicalconnection is already established or the wireless connection is enabledin response to a user input.
 20. The medium of claim 18, wherein themethod further comprises: controlling which of at least two differentrespective wireless access technologies is employed for communication ofthe media data between the mobile device and a network; generating mediainterface data indicating which of the at least two different respectivewireless access technologies is being used for communicating the mediadata between the mobile device and the network, controlling which of thephysical or wireless connections between the docking station and themobile device is used for the media channel based on the media interfacedata.